Public dispatch chatroom

ABSTRACT

A system and method of conducting a dispatch multi-party communication session is disclosed. In accordance with an embodiment of a method of the present invention, the method includes establishing a dispatch multi-party communication session in a dispatch network and identifying the dispatch multi-party communication session to a subscriber of the dispatch network. A join request is received at the dispatch network from the subscriber in response to identifying the dispatch multi-party communication session and the subscriber is joined to the session in response to the received join request. In accordance with an embodiment of a system of the present invention, the system includes a dispatch network wherein the network establishes a dispatch multi-party communication session and identifies the dispatch multi-party communication session to a subscriber of the dispatch network. The dispatch network joins the subscriber to the dispatch multi-party communication session in response to a join request received at the dispatch network from the subscriber.

This application claims the benefit of U.S. Provisional Patent Application Ser. No. 60/610,554, filed Sep. 17, 2004, and U.S. Provisional Patent Application Ser. No. 60/689,079, filed Jun. 10, 2005, the disclosures of which are herein expressly incorporated by reference.

FIELD OF THE INVENTION

The present invention relates generally to the field of telecommunications, and in particular, to a public dispatch chatroom.

BACKGROUND OF THE INVENTION

Cellular communications systems typically provide interconnect and/or dispatch voice communication services. Interconnect voice communication services are those typically provided by most cellular carriers as circuit-switched communications. Dispatch communication services are commonly known as a “walkie-talkie” type of call, such as provided by Nextel Communications, Inc. and identified by the trade names Push-To-Talk (PTT) or Direct Connect. The popularity of dispatch calls is ever expanding and this increase in popularity has created a demand for more features to be associated with these types of calls.

Currently, dispatch communication services can typically provide private and group calls. A private dispatch call is between two parties, while a group dispatch call is between more than two parties, each of whom can converse with each of the other participants during the call. Group calls are becoming increasingly popular because they allow a subscriber to converse with numerous other subscribers in the same session. This provides particular utility in both business applications and for social communications. However, there are aspects in the way dispatch group calls are conducted today that may not be desirable in all circumstances.

One such aspect is that currently dispatch group calls are generally conducted between group members for groups that are pre-defined prior to the calls. For example, if a business person regularly needs to communicate with certain other people in the business, the person can define a group to include these other people and upon initiation of a group call to these persons, all are automatically connected into the group call if they are available, e.g., their phone is turned on and they are not utilizing the phone to communicate with someone else. Therefore, in a group call with a pre-defined group, while having significant utility, the group must be defined prior to the call, thus, reducing some of the flexibility for defining the group that may be desired in certain circumstances.

Another current method of establishing a group call that may have potential drawbacks in particular circumstances is to dynamically establish the group for the call. In this method, the group is not required to be pre-defined, as discussed above, but rather, the group members are selected by the initiator of the group call in conjunction with establishing the group call. This methodology may be referred to as a selective dynamic group call since the group members are selectively defined by the call initiator and also are dynamically defined, i.e., not pre-defined.

Whereas the selective dynamic group call can provide further flexibility over the pre-defined group call, this type of group call may also have limitations in certain circumstances. With both the pre-defined group call and the selective dynamic group call, a group must be defined for the call by a party to the call. Therefore, in the currently known methods, if a dispatch multi-party communication is to be conducted, the parties that are to participate in the communication must be known. However, there are circumstances where it may not be known who should participate in the call. For example, if a group call was being conducted between people that have an interest in a particular topic, e.g., the traffic situation on a particular highway, it is not possible to define a group that included every possible person that may have an interest in participating in the group call. Therefore, there would be some individuals who would desire to participate in the call, however, because their identity may not be known to the group owner/chairperson of the call, they are not able to define these individuals as being part of the group, and thus, they would not be able to participate in the call. Thus, current methods for conducting dispatch multi-party communications require a potential participant to be identified by a party to the call in order to participate. If the potential participant is not known to a party to the call, the potential participant may not be able to participate.

Therefore, it would be desirable to provide an improved dispatch multi-party call capability. The improved capability could provide greater flexibility for composing the participants in the multi-party call.

SUMMARY OF THE INVENTION

In accordance with an embodiment of a method of the present invention, a method for conducting a dispatch multi-party communication session is provided. The method includes establishing a dispatch multi-party communication session in a dispatch network and identifying the dispatch multi-party communication session to a subscriber of the dispatch network. A join request is received at the dispatch network from the subscriber in response to identifying the dispatch multi-party communication session and the subscriber is joined to the session in response to the received join request.

In accordance with an embodiment of a system of the present invention, the system includes a dispatch network wherein the dispatch network establishes a dispatch multi-party communication session and identifies the dispatch multi-party communication session to a subscriber of the dispatch network. The dispatch network joins the subscriber to the dispatch multi-party communication session in response to a join request received at the dispatch network from the subscriber.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a public dispatch chatroom in accordance with the principles of the present invention.

FIG. 2 illustrates an embodiment of a method for conducting a public dispatch chatroom in accordance with the principles of the present invention.

FIG. 3 illustrates an embodiment of a method of inviting a party to participate in a dispatch public chatroom in accordance with the principles of the present invention.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

FIG. 1 illustrates an exemplary method and system in accordance with an embodiment of the present invention. As described in more detail below, in accordance with the principles of the present invention, a dispatch multi-party communication session may be conducted as a public dispatch chatroom which includes a plurality of client communication devices A-F communicating through the dispatch network. The dispatch network 100 includes a dispatch communication system 110 and an access network 120, which may be either a wire-less or wire-line network. The dispatch network uses the signaling server 130 and media server 140 to support the public dispatch chatroom communications. Signaling server 130, among other functions, performs call set-up, floor control and access, and call termination functions for the dispatch communication session. Signaling server 130 may include, or be coupled to, chatroom definition database 132. As will be explained further later in this specification, database 132 may contain configurable parameters for the public chatrooms and a directory 134 of available public chatrooms. The client devices can be mobile telephones, IP-based telephones, desktop computers, or any other type of device which is capable of dispatch communications. As will be further explained later in this specification, one of the client devices can be associated with a chairperson of the chatroom.

Public chatrooms can be pre-defined in database 132 through a telecommunications service provider network, such as a cellular network operator. They can be defined via a web-based client or handset with a session initiation protocol (SIP) uniform resource locator (URL) and a chairperson SIP address with specific privileges. Any subscriber to network 100 may establish a public chatroom through the network and the participation in the chatroom is open to any subscriber, i.e., the chatroom is public. Thus, a subscriber that desires to participate in a public chatroom does not need to be defined as a member of a group for the dispatch multi-party session, nor does the subscriber need to be invited to join the session.

Further with respect to public dispatch chatroom database 132, the database contains configurable parameters for the particular chatrooms. For example, the database can be configured with information regarding the maximum number of participants, the duration of the chatroom, the person(s) with chairperson privileges, etc. The person responsible for establishing the chatroom, and/or the chairperson, may set the configurable parameters through network 100. Once these parameters are set, the signaling server 130 utilizes this information in supporting the conduct of the public chatroom.

In accordance with an embodiment of a method of the present invention, as can be seen in FIG. 2, to conduct a dispatch public chatroom, in step 200 a dispatch multi-party communication session is established in the dispatch network. The session can be established by dedicating the network resources, e.g., the signaling server and media server, to conduct the session and defining the parameters of the chatroom in database 132. In step 210, the public chatroom is given a title to identify the session, e.g., a name that reflects the subject matter of the session or the sponsor of the session. In step 220, the session is identified to subscribers of the network to make them aware of the existence of the chatroom.

The present invention is not limited to any methodology for identifying the public chatroom to the network's subscribers. All that is required is that the subscribers be able to become aware of the public chatroom so that they can participate if they desire. For example, as will be further discussed below, the names and/or addresses of the public chatrooms can be stored in the network for access by the subscribers. Thus, the subscriber could query the directory 134 to obtain a listing of available public chatrooms. Alternatively, the network can provide the available chatrooms to the subscribers. The network can either directly provide the names/addresses to the subscribers, e.g., by sending them to their mobile phone, or can indirectly provide them, e.g., by posting the address on a publicly viewable sign. An example of an indirect posting could be a highway electronic sign that informs network subscribers of a public chatroom that has been recently established to discuss delays occurring on the subject highway.

Continuing in step 230, if a subscriber desires to participate in a public chatroom, the subscriber can send a join request to the dispatch network in response to the identification of the chatroom and, in step 240, the network then joins the subscriber to the public chatroom if it already has other participants. If the chatroom has been established but does not currently have any participants, in response to the join request, the network will start or restart the chatroom. In step 230, all that is required is that the subscriber communicate to the network that the subscriber desires to join a particular public chatroom. The “join request” is not limited to any particular methodology, format, or content, rather, it is merely an indication by the subscriber to the network that the subscriber desires to participate in the public chatroom. It could be as simple as selecting a public chatroom from a listing of public chatrooms on the subscriber's phone by using the telephone's keypad. Similarly, step 240 does not require any particular methodology for joining the subscriber to the public chatroom by the network. All that is required is that the network connect the subscriber to the public chatroom so that the subscriber can participate in the chatroom.

As discussed above, the network will identify public chatrooms to subscribers and users have the ability to browse current chatrooms and select/join as they wish. In accordance with an embodiment, a user accesses the chatroom by scrolling through available chatrooms in the public chatroom directory 134, separated by category, e.g., sports, traffic, personals, etc. The user highlights the chatroom she wishes to join and then presses the join softkey. A user may also enter the full address of the chatroom and select join, highlight the chatroom address from the call history list and select join, or select the address saved to her phonebook and join from there. Thus, dispatch users may join any public chatroom available without having to receive an invitation. Upon “joining” a chatroom, a user is placed directly into the chatroom and may be notified via text and an audible tone that she is active. Once the user is active in the call, the dispatch button becomes enabled to request the floor.

Thus, as discussed above, the potential participants in the public chatroom dispatch call are not required to be included in a defined group; this is in contrast to the method of how certain group calls are currently established by using a defined group. The present invention provides the flexibility of conducting a chatroom based on an individual's own desire and initiative to participate as opposed to requiring a third party's initiative to include the individual in the chatroom, e.g., by including the individual in a defined group or inviting the individual to participate.

However, in accordance with another feature of the present invention, a dispatch user may send an invitation to join any public chatroom to any other dispatch user. Thus, a subscriber may receive an invitation to join a chatroom from the chairperson or other participants in the public chatroom. When an invitation is sent, the inviter is immediately placed into the chatroom. The called party(s) will receive the invitation with the time/date stamp and are given the option to join, decline, or snooze the invitation by pressing the appropriate softkey. The invitation can be sent using a short message service (SMS) message or the like. In an immediate chatroom invite, as soon as the chairperson sends the invitation, he/she is immediately placed into the chatroom and waits for others to join.

Each called party may decide whether to opt-in to the chatroom. That is, the called party is not a participant in the chatroom unless the called party accepts the invitation to join the chatroom. If the called party either declines the invitation or defers acting on the invitation, the called party is not a participant in the chatroom, i.e., does not hear audio communications from, nor provide communications to, other participants in the chatroom.

The present invention is not limited to any particular methodology for sending an invitation to a called party. All that is required is that a participant is able to identify potential participants for the chatroom and identify those participants to the dispatch network. The dispatch network sends an invitation to each potential participant that includes options for participation. The invitation can be in an audio-visual format where the recipient receives both an audible indication at their phone that they have been invited to participate and a visual indication that can be displayed on the phone. As discussed above, the invitation can also be sent as a text message, e.g., a short message service (SMS) message.

In accordance with another feature of the present invention, invitations can be sent for chatrooms scheduled to take place in the future. The chairperson or person sending the invitation sets the time and date of the chatroom in the invitation menu prior to sending the invitation. The invited party(s) receive the invitation and the invitation states the time and date of the scheduled chatroom. Any invitee can accept the invitation by pressing the “accept” soft key and the time/date of the chat will be stored, decline the invitation, or respond tentatively to the invitation. The sender of the invitation has the option to receive audible and UI messages notifying him that one of the invitation recipients has responded to the invite. For those invitees who have accepted or are tentative, at the actual start of the chatroom, they will be prompted to join, decline, or snooze the invitation. The sender of the invitation can check a roll call to see who has accepted/declined/tentatively accepted the invitation and who has not yet responded. Finally, the sender can set up and send an invitation with an automatic reminder so that each invitee is reminded of the call just prior to the chatroom starting.

As illustrated in FIG. 3 in an embodiment of a method of the present invention, in step 300 the dispatch user is able to select members for participation from his telephone's phonebook or enter new addresses for members not in the phonebook. After selecting the individuals or entering user addresses, in step 310 the inviter can actuate a soft key on the inviter's telephone to send the invitations to the potential participants to join the public chatroom via the network.

After the inviter sends the invitations, he is placed directly into the chatroom if he is not already a participant, as illustrated in step 320. The potential participants will receive the invitation in step 330 with a time/date stamp and, as discussed above, are given the option to join in step 340. In response to the option to join, the invitee may either accept the invitation and join the chatroom in step 342, decline the invitation in step 344, or snooze the invitation in step 346, e.g., defer the invitation, by pressing an appropriate softkey.

The inviter may also send a chatroom invitation while he is active in a current public chatroom. While in the chatroom, the inviter may enter a chatroom menu and select “invite” as he would when setting up a new invitation prior to joining a chatroom. The inviter also has the option to receive/disable audible and user interface (UI) messages notifying him that an invite recipient has joined/declined/snoozed the chatroom invite.

The default text message appearing on the UI of an invitation recipient is “Chat invite received from “username””. An inviter may also configure his own text message to be sent instead of the default message or select from a list of predefined invite messages, such as “urgent”, “attendance required”, “please join”, etc.

As shown in step 342, pressing the “join” softkey places the invitee directly into the chatroom. Acceptance of the invite by the invitee causes the invitee to be joined to the chatroom by the dispatch network. The participant will be notified that he is active in the chatroom in step 342A, for example, via text and/or an audible tone. Once the participant is active in the call, the dispatch button on the telephone handset becomes enabled to request the floor in the dispatch public chatroom as illustrated in step 342B. As is well known, dispatch communications are half-duplex communications where only one person at a time is able to speak. When a party has the “floor” they are able to speak during the session.

If the invitee does not respond to the invitation after a specified amount of time, e.g., if the invitee has snoozed the invite, the UI returns to its idle state and a notification is placed in the invitee's telephone “missed call” log with a time/date stamp as illustrated in step 346A. When the user is checking their missed calls, the user is given the option to join the chatroom in step 346B or ping the network in step 346C to determine if the chatroom is still in session. If it is still active, i.e., at least 1 user is in the chatroom, the user is given the option to join the chatroom in step 346D. If there is no one else in the chatroom, the user is notified that there is no one in the chatroom and the user is then prompted to return to the main menu. Alternatively, the chatroom invitation can be cleared from the user's device upon expiration of the chatroom and/or the user can be provided with a recording of the chatroom session. If the missed call is for a future chatroom invitation, the user has the option to accept/decline/tentatively accept the chatroom invitation.

Further regarding the options of snoozing the invitation and declining the invitation, if a user snoozes the invitation, in step 346E the present invention may re-prompt the user to join the chatroom after a period of time. The user may then join the chatroom, as shown in step 346F. If the user declines the invitation, in step 344A the user's handset may be placed back into its idle state. Also, similar to the process described above regarding snoozing the invite, if the user declines the invitation a notification is placed in the invitee's telephone “missed call” log with a time/date stamp as illustrated in step 344B. From the missed call log, the user can join the chatroom in step 344C or ping the network in step 344D to determine if the chatroom is still in session. If it is still active the user is given the option to join the chatroom in step 344E. If there is no one else in the chatroom, the user is notified that there is no one in the chatroom and the user is then prompted to return to the main menu. Alternatively, the chatroom invitation can be cleared from the user's device upon termination of the chatroom and/or the user can be provided with a recording of the chatroom session.

The status of the invitees will be available to the chairperson or the person who sent the invitation. A user can also set up personal reminders for chatrooms so that a notification will be sent to themselves at the time of the chatroom for prompting the user to join the chatroom, decline the chatroom, or snooze the reminder. In the event that a user is out of the network's coverage area or not powered-up when a reminder is scheduled, the user will be reminded of all missed reminders upon power-up or reentering the network's coverage area. Additionally, if invitations were directed to the user during an out-of-coverage or powered-down timeframe, the user will be prompted accordingly to consider the invitations upon power-up/regaining of coverage. The invitations sent during these times will be stored until the user can receive them.

Upon joining a public chatroom, the user may converse with anyone else (unless privileges are denied by the chairperson) in the room and all participants who have joined the chatroom will be able to hear all conversation. When the floor is open, the user interface (UI) and an audible tone alerts the participants as such. When the participant tries to take the floor and is unsuccessful, there will be a distinct audible tone heard by that participant only, as well as when the participant is successful in taking the floor. The name or alias name of the user who owns the floor is to be displayed on all users' UIs.

Participation in the public chatroom is scalable. For example, one chatroom may be limited to 100 members on a regular basis, however, at some point needs to be changed to handle 500 members. Another chatroom may be limited to 300 members and another at 700 members. As will be discussed further below, the chairperson has the capability to scale the size of the chatroom while the chatroom is idle, i.e., no participants. As discussed previously, the size of the chatroom, along with other chatroom parameters, are configurable parameters that may be set and stored in database 132.

At any time during the public chatroom the chairperson may view a list of all participants currently on the call, all who were previously on the call and dropped off, and all who are on the call but have the session on hold, e.g., for the purpose of being on another call. Also, the chairperson may view the status of all invitees to the chatroom, e.g., declined, snoozed, currently on call, on hold, previously on call and dropped off, etc. If the chairperson switches to another call and places the public chatroom on hold, he will not receive audible tones and text informing him of who is joining the call, in the event he requested this capability from the network when sending invitations. However, the chairperson may view the public chatroom role call to see who is on the call through chatroom monitoring.

Chatroom participants have the ability to maintain anonymity by creating an alias address. When a user sends an invitation or receives one, he has the option to join the chatroom under an alias name. Using an alias name will provide the user with privacy/anonymity, if desired. When sending an invite, the user may either select from a list of names he has set up in his personal options or can enter a new alias name under which he wants to send an invitation. When accepting an invite, the user can be prompted for an alias name under which he would like to join the chatroom. The user could then select from the list of names he has set up in his personal options or can enter a new alias name. If the user enters the chatroom with a duplicate alias name, i.e., one that is already in use by another chatroom participant, he can enter the chatroom with the selected alias but with a number provided after the alias name to distinguish him from the other participant, e.g., John(1).

Each participant in a chatroom will only be able to see the alias address, and not the primary address, of other participants. Therefore, as discussed above, a participant can maintain anonymity and protect the privacy of his personal address with respect to other participants. However, when an invitee accepts an invitation and uses an alias address, in an embodiment, the public chatroom chairperson receives a notification that “JaneDoe@nextel.com” has accepted the invitation and has entered the chatroom as “Janie”.

Because there may be a possibility that an invitee may attempt to utilize an alias that may be inappropriate and/or offensive to certain other participants, the dispatch network may filter the alias selected for use by a participant prior to its use for a determination as to its acceptability. A user who attempts to use an inappropriate alias address, as determined by reference to a database of restricted words, will be re-prompted to either select a different alias address, enter the chatroom by using his primary ID, or not enter the chatroom. The chairperson is also able to restrict an invitee from joining the chatroom under an alias that is not acceptable as determined by the chairperson.

In order to accurately monitor and control the chatroom, the chairperson is able to see the primary account address of a user regardless of what alias the user may be using. For example, if an individual has been banned from a chatroom, he will not be able to re-enter merely by changing his alias name.

If a participant is acting inappropriately in the chatroom, the chairperson can view the user's primary ID and temporarily block him from the chatroom, making him unable to continue conversation in the chatroom since he would be dropped from the call. A UI message is sent to the user notifying him that he has been blocked. The chairperson can also permanently block him from returning to the chatroom indefinitely by blocking his primary user ID. The user will not be able to re-enter merely by changing his alias address. The chairperson of the public chatroom, and anyone else the chairperson enables with chairperson privileges for a specific chatroom, are the only individuals that may view primary user IDs and block users.

In the present invention, the blocking options include:

-   -   temporarily blocking a user for a configurable duration, e.g.,         24 hours, with a warning being sent to the user;     -   permanently blocking the user from the chatroom after a         specified number of blocks, with notification being sent to the         user; and     -   entering narrative text in a text box by the chairperson         describing the reason for the block and/or any other pertinent         information regarding the block.

As with the other configurable parameters for the public chatroom, the blocking options may be set in database 132. Signaling server 130 implements the set blocking parameter in conducting the public chatroom session.

A system configurable chatroom timer provides the public chatroom with a hang time feature. Therefore, if all participants exit a public chatroom, the chatroom will remain “active” for a specified period of time, i.e., the hang time, and will not automatically time-out. After the hang time expires, the public chatroom will restart if still authorized and if someone enters the chatroom. Additionally, a participant may re-enter the chatroom after exiting it. The participant may re-enter prior to the expiration of the hang time or, as discussed above, after the hang time expires if still authorized.

The user has three options for saving the chatroom address to his phonebook. After participating in the chatroom, the address of the chatroom can be stored in the user's “Call History” list and the user may save the address to his local phonebook eliminating the need to locate this chatroom again through the chatroom directory. A second option is for a user to identify a chatroom from the public chatroom directory and save the address to his phonebook without joining the chatroom. The third option is for a dispatch user to directly enter and save the address to his phonebook.

The public chatroom may be sponsored by a company, individual, or any other entity. The sponsor is the entity that is responsible for establishing the existence of the chatroom. The sponsor may also manage the parameters of the chatroom. For example, the sponsor could determine whether the public chatroom would always be in session or only be in session for scheduled times and topics, be conducted for either a specified discussion topic or to provide an open forum for discussion, and determine how the chatroom would be identified to the subscribers. The sponsor could also be the chairperson of the chatroom or could designate a person to be the chairperson, if the chairperson functionality is implemented. It is not required that the sponsor be a participant in the chatroom.

Further to the above, the public chatroom can be sponsored by the telecommunications service provider, e.g., the dispatch carrier. In this case, the dispatch carrier owns its own chatroom SIP addresses, e.g., chatroom addresses for public chatrooms related to the topics of Route 66, beach traffic, etc., and would also manage the number of participants permitted in the chatroom and the administration of the chatrooms, e.g., by a carrier chairperson.

The following are exemplary use cases for a public chatroom in accordance with the principles of the present invention.

Martha wishes to join a chatroom. Martha browses the chatrooms that are available through the chatroom directory, highlights the chatroom of interest, and joins by selecting the join softkey. Martha is immediately placed into the chatroom and may begin conversing with others using the dispatch button to take the floor. After Martha ends her participation by hitting the end key, she goes to her call history list and saves the chatroom address to her phonebook for future use.

John joins public chatroom ABC and wishes to invite Carol, Greg and Cindy to the chatroom. John selects the option “invite others” from the menu, goes to his address book and selects the individuals he'd like to invite, and sends invitations for them to join the chatroom. Upon the invitees joining the chatroom, John receives an audio signal and text notifying him who from his invite list has joined the chat.

The Company XYZ public “Recall” chatroom is limited to 100 members. However, due to a recent new announcement on a major recall, the chatroom is temporarily changed to accommodate 500 members by the chairperson. After the effect of the recall announcement settles down, the chatroom chairperson then scales back the chatroom down to its original 100-member limit.

Another example of a public chatroom, as mentioned briefly above, can be a traffic information chatroom. For example, a public dispatch chatroom can be dedicated to a particular highway, such as Route 66 mentioned above. Accordingly, users can join the chatroom to monitor others' communications. These communications can identify accidents and/or congestion. As discussed previously, the users can be informed of the existence of the public chatroom by an electronic sign that is located, for example, on, or in proximity to, the highway. Yet another type of chatroom can be a sports-themed chatroom. For example, a chatroom can be established for a particular sport or a particular sports team.

As discussed above, in an embodiment, the public chatroom has a chairperson. While it is not required that the chatroom have a chairperson, it may be desirable for management of the chatroom since the participants in the chatroom may not be familiar to the sponsor, for example. This is in contrast to known methods for establishing dispatch group calls where the group members are defined and presumably known by the call participants. The chairperson may be the party who set up the chatroom or who is designated through the set up process or may be another participant in the chatroom as designated by the sponsor. The chairperson may be a wireless network operator's employee, where a wireless network operator sponsors its own chatrooms or the chairperson may be someone designated from a company-sponsored public chatroom. The chairperson may have the following privileges, which are not intended to be all inclusive, but rather, are to be understood in conjunction with the entirety of this specification: Chairperson Privileges View logistics of the chatroom (e.g., member list, priority levels) View the users' primary IDs to properly manage the chatroom Merge two chatrooms together (by a chairperson who is the chairperson for both chatrooms) and view the details of both chatrooms together View roll call to see who is on the call at any given period of time, who was on the call but now has dropped off the call, and who has put the call on hold Monitor the chatroom while actively participating. Monitoring a chatroom may consist of viewing active participants, participants who are “active” but in another session, participants who were active but have exited, listening to chatroom conversations, and viewing chatroom conversations via text from the desktop Monitor the chatroom while not participating - (Voice to text capabilities support multiple window viewing of chatrooms on the desktop) Scale the size, i.e., the number of possible participants, of the chatroom while the chatroom is idle Tear down a chatroom Take the floor at any time Send text messages to a participant Break into a session, i.e., enter or become active in a chatroom that is being passively monitored Manage audio and text signals, e.g., to all in the chatroom when someone has entered or exited Ability to turn on/off audible tones/messages/UI receipts/notifications of people joining/exiting a chat Manage a question/answer session Actively participate in the chatroom Send invites to users for the respective chatroom Manage the privileges and/or memberships of users, including: Enable or disable select participants from taking the floor during the chatroom, e.g., in a broadcast type of chatroom Disconnect one or many participants without interrupting the chatroom Disable one or many participants from rejoining the chatroom (temporarily or permanently) Block users from entering a chatroom Assign priority levels to members to enable greater floor control Delegate a subset of, or all, chairperson privileges to another chatroom member Enable/disable ability of users to send invitations

As discussed above, the chairperson may delegate all or a subset of the chairperson's privileges to one or more chatroom participants. In this circumstance, there may be a number of chairpersons, however, the original chairperson may still maintain absolute control over the chatroom, i.e., they can overrule decisions made by the other delegated chairpersons. The chairperson may assign his privileges to another individual while maintaining his own rights as chairperson.

The below are exemplary use cases for several of the privileges discussed above for the functionality of the public chatroom chairperson.

Rita is the chairperson of a public chatroom. Rita is monitoring the chatroom and notices that a particular participant is acting inappropriately. Rita goes into the chatroom set up on her desktop, identifies the user, and terminates him from the chatroom. The termination is tagged to the primary user name, regardless of whether or not the user is using an alias name in the chatroom, so that further entry into the chatroom is prohibited regardless of the alias name used, if any.

Bill is the chairperson for the ABC company public chatroom which is sponsored by the ABC company. During the chatroom, a presentation will be made and, because this is a company sponsored chatroom, the company wants to prevent interruptions during the presentation. Therefore, Bill, through his chatroom menu options blocks all participants other than the presenter(s) from taking the floor during the presentation. When the presentation is over, Bill is able to unblock the other participants so that questions can be asked.

An additional functionality the chairperson has in the present invention is the ability to monitor and manage the chatroom remotely, e.g., from an internet web client device. Thus, the chairperson is able to exercise all of his privileges as discussed above remotely. For example, the chairperson is able to view participants, block participants, shut down the chatroom, start the chatroom, restrict membership (e.g., one user, a group of users via a domain, or by allowing a specific domain), disconnect participants, etc., from any remote device, e.g., a desktop computer, laptop, PDA, handset, etc. In an embodiment, as shown in FIG. 1, client device F of the chairperson would be a desktop computer with an interface to the chatroom. The chairperson would be able to hear the audio from the chatroom on the desktop as well as control the chatroom from it, as discussed above.

The below are exemplary use cases for the use of a remote device by the public chatroom chairperson.

Tom begins a chatroom by launching the chatroom from his desktop web client. From his web interface, Tom is able to see who is on the call and can provide the sponsoring company with a list of participants.

Sharon is monitoring a chatroom from her web interface. From the web she is able to disconnect one of the members who is acting inappropriately and block him from returning to the chatroom.

In accordance with another aspect of the present invention, any chatroom participant can send a text message sidebar communication to any other chatroom participant. The sidebar communication is only communicated to the sidebar participants and is not communicated to any other participant in the public chatroom.

The following table summarizes the features and functionalities of a public chatroom in accordance with the principles of the present invention and exemplary embodiments thereof. This table is not intended to be all inclusive, but rather, is to be understood in conjunction with the entirety of this specification: Any user can join the chatroom Any user can start the chatroom Companies can manage own chatroom Address predefined through service provider (e.g., Nextel) Open participation (any user can join) Any participant can send invites to other users Directory of available chatrooms Scalable participation size (in increments of 10) Alias addresses enabled Join a call using a “join” softkey Join a chatroom without receiving an invitation Initiate a chatroom (chatroom pre-exists so would not be initiated but anyone could join) Save chatroom address to phonebook Reinitiate a chatroom (pre-exists so would not be initiated but anyone could join) Users may opt-in to a chatroom when receiving an invitation User may join a chatroom without receiving an invitation The chairperson is preauthorized with certain privileges Any user can send an invitation Any user can invite a participant to a chatroom after the chatroom is in session Participant receives notification that he is active in the call via audible tone and text message Invitations can be sent using a default or user configurable text message to appear on invitee's UI Target who missed an invitation can ping network to see if chatroom still in session and join Decline a chatroom invitation Snooze a chatroom invitation Any user can send a text message sidebar to another chatroom participant Any user can view list of chatroom participants (alias address is what is provided)

The disclosed embodiments are illustrative of the various ways in which the present invention may be practiced. Other embodiments can be implemented by those skilled in the art without departing from the spirit and scope of the present invention. 

1. A method for conducting a dispatch multi-party communication session, comprising the acts of: establishing a dispatch multi-party communication session in a dispatch network; identifying the dispatch multi-party communication session to a subscriber of the dispatch network; receiving a join request at the dispatch network from the subscriber in response to the act of identifying the dispatch multi-party communication session to the subscriber; and joining the subscriber to the dispatch multi-party communication session in response to the received join request.
 2. The method of claim 1 further comprising the acts of: receiving an invitation to join the dispatch multi-party communication session directed to a called party at the dispatch network; transmitting the invitation to the called party by the dispatch network; receiving an acceptance to join the dispatch multi-party communication session from the called party at the dispatch network in response to the invitation; and joining the called party to the dispatch multi-party communication session by the dispatch network.
 3. The method of claim 1 further comprising the act of designating a chairperson for the dispatch multi-party communication session.
 4. The method of claim 3 further comprising the act of displaying a list of participants in the dispatch multi-party communication session to the chairperson.
 5. The method of claim 3 further comprising the act of monitoring the dispatch multi-party communication session by the chairperson through an internet interface.
 6. The method of claim 3 further comprising the act of assigning a priority to the subscriber by the chairperson.
 7. The method of claim 3 further comprising the act of assigning a function of the chairperson to the subscriber by the chairperson.
 8. The method of claim 3 further comprising the act of preventing the subscriber from providing audio during a portion of the dispatch multi-party communication session by the chairperson.
 9. The method of claim 3 further comprising the act of joining the dispatch multi-party communication session to a second dispatch multi-party communication session by the chairperson.
 10. The method of claim 2 further comprising the act of snoozing the invitation by the called party and wherein the act of snoozing occurs prior to the act of receiving the acceptance at the dispatch network.
 11. The method of claim 10 further comprising the act of providing a notification to the called party in response to the act of snoozing the invitation.
 12. The method of claim 10 further comprising the act of determining whether the dispatch communication session is active and wherein the act of determining occurs subsequent to the act of snoozing.
 13. The method of claim 1 wherein the act of identifying the dispatch multi-party communication session to the subscriber includes the act of storing a name of the dispatch multi-party communication session in the dispatch network.
 14. The method of claim 1 wherein the act of identifying the dispatch multi-party communication session to the subscriber includes the act of providing a name of the dispatch multi-party communication session to the subscriber.
 15. The method of claim 14 wherein the name is provided to a dispatch device of the subscriber.
 16. The method of claim 14 wherein the name is displayed on a publicly viewable sign.
 17. The method of claim 1 further comprising the act of identifying the subscriber to other participants in the dispatch multi-party communication session by an alias name.
 18. The method of claim 2 wherein the act of transmitting the invitation to the called party by the dispatch network includes the act of transmitting the invitation as an audiovisual message.
 19. The method of claim 2 wherein the act of transmitting the invitation to the called party by the dispatch network includes the act of transmitting the invitation as a text message.
 20. The method of claim 1 further comprising the acts of: receiving an invitation to join the dispatch multi-party communication session directed to a called party at the dispatch network; transmitting the invitation to the called party by the dispatch network; and providing an option to the called party to either accept the invitation, decline the invitation, or defer the invitation by the dispatch network.
 21. The method of claim 20 further comprising the acts of: receiving an acceptance to join the dispatch multi-party communication session from the called party at the dispatch network in response to the invitation; and joining the called party to the dispatch multi-party communication session by the dispatch network.
 22. The method of claim 20 wherein if the called party does not either accept or decline the invitation after a defined period of time a notification is stored on a dispatch device of the called party.
 23. The method of claim 22 further comprising the act of providing the called party with an option of joining the dispatch multi-party communication session in response to the notification.
 24. The method of claim 22 further comprising the act of determining by the called party in response to the notification whether the dispatch multi-party communication session is still being conducted.
 25. The method of claim 20 wherein if the called party does not either accept or decline the invitation after a defined period of time the called party is prompted to join the dispatch multi-party communication session.
 26. The method of claim 1 further comprising the act of blocking the subscriber from participating in the dispatch multi-party communication session after the subscriber is joined to the session.
 27. The method of claim 20 wherein the act of transmitting the invitation to the called party occurs prior to the act of establishing the dispatch multi-party communication.
 28. The method of claim 27 further comprising the act of providing a reminder to the called party prior to the act of establishing the dispatch multi-party communication.
 29. The method of claim 20 further comprising the act of prompting the called party to consider the option when the called party is not able to receive the transmitted invitation.
 30. The method of claim 20 wherein a notification is provided to the called party at a time associated with a start of the dispatch multi-party communication session.
 31. The method of claim 30 wherein the notification is provided to the called party in response to a reminder set up by the called party.
 32. The method of claim 30 wherein if a dispatch device of the called party is either not powered-up or out of a coverage area of the dispatch network at the time associated with the start of the dispatch multi-party communication session then the notification is provided to the called party upon either the dispatch device powering-up or reentering the coverage area of the dispatch network.
 33. The method of claim 1 further comprising the act of receiving a query from the subscriber at the dispatch network related to a second dispatch multi-party communication session established in the dispatch network.
 34. The method of claim 1 wherein the act of identifying the dispatch multi-party communication session to the subscriber includes the act of providing an address of the dispatch multi-party communication session to the subscriber.
 35. A system for conducting a dispatch multi-party communication session, comprising: a dispatch network, wherein the dispatch network establishes a dispatch multi-party communication session and identifies the dispatch multi-party communication session to a subscriber of the dispatch network and further wherein the dispatch network joins the subscriber to the dispatch multi-party communication session in response to a join request received at the dispatch network from the subscriber.
 36. The system of claim 35 wherein the dispatch network identifies the dispatch multi-party communication session to the subscriber by providing a name of the dispatch multi-party communication session to the subscriber.
 37. The system of claim 36 wherein the name is provided to a dispatch device of the subscriber.
 38. The system of claim 36 wherein the name is displayed on a publicly viewable sign.
 39. The system of claim 35 wherein the dispatch network identifies the dispatch multi-party communication session to the subscriber by storing a name of the dispatch multi-party communication session in the dispatch network.
 40. The system of claim 39 wherein the name is stored in a database.
 41. The system of claim 35 wherein the dispatch network identifies the dispatch multi-party communication session to the subscriber by providing an address of the dispatch multi-party communication session to the subscriber.
 42. The system of claim 35 wherein the dispatch network identifies the dispatch multi-party communication session to the subscriber by storing an address of the dispatch multi-party communication session in the dispatch network.
 43. The system of claim 42 wherein the address is stored in a database. 